Method of making a coexistence decision on centralized topology

ABSTRACT

Disclosed is a radio technology independent method for coexistence among dissimilar or independently operated TV Band Device (TVBD) networks and dissimilar TV Band Devices. A resource allocation method on centralized topology is disclosed, which comprises steps of receiving at least one available resource; performing a neighbor set calculation based on the received at least one available resource; calculating the resource according to the neighbor set calculation, where the calculated resource is allocated to at least one device.

TECHNICAL FIELD

The present invention relates to a radio technology independent methodsfor co-existence among dissimilar or independently operated TV BandDevice (TVBD) networks and dissimilar TV Band Devices.

BACKGROUND ART

Recently, a radio technology allowing unlicensed wireless devices canoperate in unused TV channels, which is referred to as “TV white space”has been considered. The unused TV white space channels are those notutilized by TV broadcasts, CATV headend, or other licensed devices in agiven geographic location.

The unused TV channels can be suited for Wi-Fi or other unlicensedwireless Internet services. Access to the unused TV channels wouldfacilitate a market for a low-cost, a high-capacity, mobile wirelessbroadband networks.

DISCLOSURE OF INVENTION Technical Problem

In past few years, the radio technology methods for using TV white spacehas been considered. However, a standard method to most effectively useTV white space by providing standard coexistence methods amongdissimilar or independently operated TV band device networks anddissimilar TV band devices, have not been proposed.

Solution to Problem

Therefore, an object of the present invention is to effectively use TVwhite space (TVWS) by providing standard coexistence methods amongdissimilar or independently operated TV Band Device (TVBD) networks anddissimilar TV Band Devices.

To achieve the object of the present invention in accordance with oneembodiment, there is provided a method of allocating a resource inwireless communication system, the method comprising: receiving, by acoexistence discovery and information server (CDIS) entity, at least oneavailable resource from a TV database (TVDB) entity; performing, by theCDIS entity, a neighbor set calculation based on the received at leastone available resource, wherein the neighbor of at least one coexistencemanager (CM) entity is calculated by the neighbor set calculation; andcalculating, by the CDIS entity, the resource according to the neighborset calculation, wherein the calculated resource is allocated to atleast one TV band device (TVBD).

Further, to achieve the object of the present invention in accordancewith one embodiment, there is provide an apparatus for allocating aresource in wireless communication system, the apparatus comprising: acontroller to perform the steps of; receiving at least one availableresource from a TV database (TVDB) entity; performing a neighbor setcalculation based on the received at least one available resource,wherein the neighbor of at least one coexistence manager (CM) entity iscalculated by the neighbor set calculation; and calculating the resourceaccording to the neighbor set calculation, wherein the calculatedresource is allocated to at least one TV band device (TVBD).

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is an exemplary IEEE 802.19.1 network architecture which thepresent invention is applied;

FIG. 2 is an exemplary IEEE 802.19.1 reference model which the presentinvention is applied;

FIG. 3 is an exemplary procedure for TVBD discover which the presentinvention is applied;

FIG. 4 is an exemplary procedure for coexistence manager (CM) discoverwhich the present invention is applied;

FIG. 5 is another exemplary procedure for coexistence manager (CM)discover which the present invention is applied;

FIG. 6 is a first exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 7 is a second exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 8 is a third exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 9 is a fourth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 10 is a fifth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 11 is a sixth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied;

FIG. 12 is a first exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied;

FIG. 13 is a second exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied;

FIG. 14 is a third exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied;

FIG. 15 is a fourth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied;

FIG. 16 is an exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with multiplecoexistence enablers (CEs) which the present invention is applied;

FIG. 17 is a first exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied;

FIG. 18 is a second exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied;

FIG. 19 is a third exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied;

FIG. 20 is an exemplary procedure for resource allocation by a mastercoexistence manager (CM) with multiple coexistence enablers (CEs) whichthe present invention is applied;

FIG. 21 is an exemplary procedure for resource allocation by a TVWSdatabase (DB) which the present invention is applied;

FIG. 22 is a first exemplary procedure for distributed topology whichthe present invention is applied;

FIG. 23 is a second exemplary procedure for distributed topology whichthe present invention is applied;

FIG. 24 is a third exemplary procedure for distributed topology whichthe present invention is applied;

FIG. 25 is a fourth exemplary procedure for distributed topology whichthe present invention is applied;

FIG. 26 is an exemplary procedure for Hybrid topology which the presentinvention is applied;

FIG. 27 is a first exemplary procedure for a master CM selection whichthe present invention is applied;

FIG. 28 is a second exemplary procedure for a master CM selection whichthe present invention is applied;

FIG. 29 is an exemplary procedure for resource allocated by registerinformation in centralized topology which the present invention isapplied;

FIG. 30 is an exemplary procedure for resource allocated by availablechannel set in centralized topology which the present invention isapplied;

FIG. 31 is an exemplary procedure for resource allocated by registerinformation in distributed topology which the present invention isapplied; and

FIG. 32 is an exemplary procedure for resource allocated by availablechannel set in distributed topology which the present invention isapplied.

MODE FOR THE INVENTION

One aspect of this disclosure relates to the recognition by the presentinventors about the problems of the related art as described above, andfurther explained hereafter. Based upon this recognition, the featuresof this disclosure have been developed.

The present invention is applied to IEEE 802.19.1 communicationtechnologies. However, the present invention may not be limited to thiscommunication type, but applicable to any wired/wireless communicationcomplying with the scope of the present invention.

The purpose of this disclosure is to most effectively use TV white spaceby providing standard coexistence methods among dissimilar orindependently operated TVBD networks and dissimilar TVBDs.

Hereinafter, description will be given of the configurations andoperations of the preferred embodiment according to the presentinvention with reference to the accompanying drawings.

Firstly, the meaning of coexistence will be described. The coexistencecan be defined as two or more devices or networks existing together atthe same time, in the same place and in the same spectrum. Here, thecoexistence can have degrees of quality, and can have metrices for goodand poor coexistence. For example, when the radio users or networksoperating efficiently in same spectrum without causing each otherharmful interference, this can be defined as good coexistence.Meanwhile, when the radio users or networks operating so as to causeinterference with resulting inefficiencies, errors, and retransmissionsfor the other users or network, this can be defined as poor coexistence.

There is a specific standard (i.e., IEEE 802 wireless standard) thatspecifics radio technology independent methods for coexistence amongdissimilar or independently operated TV band device (TVBD) networks anddissimilar TV band devices. The purpose of this standard is to enablethe family of IEEE 802 wireless standard to most effectively use TVwhite space by providing standard coexistence methods among dissimilaror independently operated TVBD networks and dissimilar TVBDs. Thisstandard addresses coexistence for IEEE 802 networks and devices andwill be useful for non-IEEE 802 networks and TVBDs.

FIG. 1 is a exemplary IEEE 802.19. 1 network architecture which thepresent invention is applied.

As illustrated in FIG. 1, the 802.19.1 system architecture may havethree logical entities and six logical interfaces. Here, the 802.19.1logical entity may be defined by its functional role(s) and interfaceswith other 802.19.1 logical entities and with external elements. Thethree logical entities may be a coexistence manager (CM), a coexistenceenabler (CE), and a coexistence discovery and information server (CDIS).The six logical interfaces may be an interface A, an interface B1, aninterface B2, an interface B3, an interface C, and an interface D.additionally, the 802.19.1 system may interact with three externalelements that are a TVWS database, a TVBD network or device, and anoperator management entity (OME).

In detail, the entities communicating with the 802.19.1 system mayincludes a TV band device (or TV band network), a TVWS database, and aoperator management entity. Here, the TV band device (or TV bandnetwork) may operate license-exempt in the broadcast television spectrumat locations where it is allowed. The TVWS Database may provide list ofchannels occupied by primary users and the operator management entitymay provide operator related information such as policies orlimitations.

The entities belonging to 802.19.1 system may include a coexistencemanager, a coexistence enabler, and a coexistence discovery andinformation server. Here, the coexistence manager (CM) may operate 1)coexistence decision making, which includes generating and providingcorresponding coexistence requests/commands and control information tocoexistence enabler(s), 2) discovery of and communication with othercoexistence managers, 3) assisting network operators in managementrelated to TVWS coexistence. The coexistence enabler (CE) may operate 1)communication between coexistence manager and TVBD network or device, 2)obtaining information, required for coexistence, from TVBD network ordevice, 3) translating reconfiguration requests/commands and controlinformation received from the coexistence manager into TVBD-specificreconfiguration requests/commands. The coexistence discovery andinformation server (CDIS) may operate 1) providing coexistence relatedinformation to coexistence managers, 2) supporting discovery ofcoexistence managers and opening interfaces between coexistencemanagers, 3) collecting, aggregating information related to TVWScoexistence, 4) connecting to TVWS database to obtain primary userinformation.

The aforementioned entities may be deployed as followings: theCoexistence Enabler (CE) may be deployed inside TV Band Device orNetwork. the Coexistence Manager (CM) may be deployed inside the TV Banddevice or network. Also, the CMs may be deployed outside TV bandnetworks. The Coexistence Discovery and Information Server (CDIS) may bedeployed outside TV band networks.

The frequency selection for unlicensed band heterogeneous networkwireless coexistence will be described.

The problem for unlicensed band heterogeneous network coexistence isthat it is not trivial as different standards follow differentprotocols. For example, each of different standards, such as cellular,WLAN, WPAN, WiMax, Wi-Fi, Bluetooth, etc follow each differentprotocols. Further, fair and efficient spectrum sharing is needed tomaximize the utilization of unlicensed spectrum. For the wirelesscoexistence with collaborative technique, the systems may need a mean tocommunicate with each other. On the other hand, for the wirelesscoexistence with non-collaborative technique, each system may operateautonomously.

As dissimilar wireless networks have different bandwidths, if differentradio system happen to be operated in the same location and same time,an interference will be occurred. Therefore, as explained above, thegoal of this disclosure is to achieve a better resource utilization byadapting efficient frequency selection or reselection method. And, thesolution is that assigning priority to the system with wide bandwidthsuch that it can select the frequency on which they would operate first.Thereafter, the other systems with relatively narrower bandwidth mayfill up the vacant bandwidths.

In order to achieve the goal of this disclosure, one of the solution isto utilize a central controller, such as a coexistence manager (CM).That is, if the centralized controller is in the presence, thecentralized controller (e.g., the CM) may select or reselect anoperating frequency for each of dissimilar band system (or devices). Or,if the common control channel is in the presence, the operatingfrequency negotiation may be performed the dissimilar band systems. Or,in fully distributed way, each system may choose the operating frequencygreedily. More specifically, before determining the operating frequency(or spectrum) each system may determine current frequency usage througha feature sensing (also, system may determine if it has the authority toforce the others to immigrate), then if there is no vacant bandwidth,the system may request for a frequency change by transmitting jammingsignal, such as training sequence of transmission, to another systemhaving a narrow bandwidth. Further, in the alternative way, a bandarranging method can be provided. That is, the frequency bands may bedivided into separated zones dedicated to each system, and each ofseparated zones is prioritized to the zone owner.

As explained above, three logical entities are defined in IEEE 802.19.1SDD. Those are a coexistence enabler (CE), a coexistence manager (CM),and a coexistence discovery and information server (CDIS). These logicalentities are defined by its functional roles and interfaces with otherentities or external elements.

For the deployment of the coexistence manager (CM), two types ofdeployment may possible. Those are a peer to peer decision making and ahierarchical decision making.

The architecture of coexistence manager design may be based on anexistence and enablement of the coexistence manager (CM)/coexistenceenabler (CE). For example, the coexistence manager/coexistence enablermay exist in all devices. Alternatively, the coexistencemanager/coexistence enabler may exist and may be enabled in masterdevices, and each system may have one or more master device. Or, thecoexistence manager/coexistence enabler may exist in master deviceswhile only some of coexistence managers are enabled.

In order to support various architectures adaptively, the presentdisclosure may propose to delegate coexistence management authority to amaster coexistence manager (CM), and to disable coexistence manager (CM)functionality for other CMs, which are not master CMs, while leavingcoexistence enabler on. That is, in a network that does not require acoexistence (i.e., a network having similar systems), a master device(e.g., BS, eNodeB, MS, etc) can be selected and all other devices maydisable its coexistence manager (CM) or coexistence enabler (CE). In anetwork that does require a coexistence (i.e., a network havingdissimilar systems), various architectures may be implemented using amaster CM enable/disable.

The database (DB) functionalities required for a wireless coexistencewill be described.

A super (or mater) coexistence manager (CM) such as coexistence database(CDB) may coordinate wireless coexistence between different TVWSnetworks or devices using backhaul connection to internet as physicalconnection between different systems. Here, one of functionalities ofcoexistence data base is to obtain information from the database (DB) inorder to set available TVWS channel at specific geological points.Further, an another functionality of the coexistence database is tocompute a coexistence contour. Especially, the neighbor discoverybetween different systems willing to operate on the TVWS may becomputed. An Another functionality of the coexistence database is tooperate as a centralized resource (e.g., spectrum) manager. Also, thecoexistence database may perform to make a coexistence whitespace map(CWM) for efficient frequency resource sharing between differentsystems. Lastly, the coexistence database may provide a common clock fortime synchronization between different systems.

A description for a coexistence contour will be given as following. Theneighbor discovery represents parameters of the radio and interferencerange of each device. The coexistence contour may be calculated by thecoexistence database (CDB) like entities identifying neighbor networkdevices for coexistence between different secondary systems. Eachnetwork's transmission power, an antenna height, and other physicalparameters that may be considered simultaneously for the coexistencecontour and separation distance. For certain systems, the coexistencecontour may be decided by its own system parameters and correspondingpath loss mode, and the separation distance may be decided from theother systems.

A description for coexistence whitespace map will be given as following.Two different methods of channel allocation by coexistence database(CDB) may be possible. A first method is that each representative ofnetworks/devices is connected to the coexistence database (CDB) makingthe information of each open to public, such that the coexistencewhitespace map (CWM) form the coexistence database (CDB) can be providedto each coexistence managers (CMs). A second method is that eachcoexistence manager (CM) is only connected to a TVWS database (DB), andit only receives available channel lists (or whitespace map) from theTVWS database (DB).

A description for a time sharing will be given as following. Acoexistence discovery information server (CDIS) may provide common clockshared by the networks to be time scheduled. Here, a least commonmultiple (LCM) of frame duration of each cellular like system may beused. A silent duration, an interval consistent with the super framestructure may be utilized. A WiFi-like systems may keep silent if thelast frame does not fit into the super frame structure.

A description for spectrum management in heterogeneous networks will begiven as following. when a channel (or resource) is allocation by thecoexistence database (CDB), the CDB may allocate the channel (orresource) to the coexistence manager (CM) omnipotently. Or, as being theintermediary, the CDB may provide a priority standard between the CMs,and may simply control the selection of channel (or resource) for eachCM. Or, the CDB may just play a role as the database only.

In a first case of spectrum management, the coexistence manager (CM) maybe implemented in an access point (AP) like device as an embedded formatand may be implemented outside of the device. Here, the AP like device(e.g., Mode2, fixed device) may have a CM's functionality, and mayselect and manage a master CM that represents a aggregation of aparticular system, a manufacture, or divided devices in spatially. Also,a master device of WPAN may have a CM functionality. The coexistencedatabase (CDB) may allocate independent resource (or channel, frequency,spectrum, etc) to each CM. Here, the allocation of resource is performeddynamically according to network topology, and the allocated set ofchannel may be notified to the CM by using the coexistence whitespacemap (CWM).

In a second case of spectrum management, the coexistence database (CDB)may designate a master coexistence manager (CM) to allow a spatial reusebetween the divided users (or devices) in spatially. Here, for aresource allocation, the master CM may obtain an interference mapbetween necessary CMs using geo-location information or neighboringinformation obtained from the CMs. In case of similar networks (ordevices), a master CM may be selected by a communication between thesimilar networks (or devices). In case of dissimilar networks (ordevices), a master CM may be selected by a negotiation between thedissimilar networks (or devices) through the coexistence database (CDB).

In a third case of spectrum management, a hierarchical layer CMstructure may be defined according to a coverage (or any otherparticular references). That is, after seeing the WM obtained from theCDB, the most upper layer CM may select a resource with consideration ofresource allocation for lower layer CMs, and the lower layer CM mayselect the resource from the available resources, which were notselected by the upper layer. This resource allocation may becontinuously repeated for all CM in lower layers.

A description for coexistence decision-making topologies will be givenas following. In this disclosure, the possible coexistence topologiesand its possible system architectures will be provided. The coexistencewhitespace map (CWM) may be adapted to realize a decision making in anytopology. Two different type of logical entities may exist, and thoseare a coexistence manager (CM) and a coexistence discovery informationserver (CDIS). The CDIS may perform to collect, aggregate and proveinformation for facilitating coexistence. And, the CM may perform adecision making. Three different types of topologies may be possible,and those are a centralized topology, a distributed topology, and anautonomous topology. In the centralized topology, a super CM (i.e.,master CM) is utilized. That is, the CDIS is performed mainly for datastorage and data processing, the super CM may serve all the neighboringnetworks, and the one of the TVBD within interfering networks may be thesuper CM. in the distributed topology, the CDIS is performed tofacilitate opening interfaces between the CMs, the CM may exchangeinformation required for coexistence, and the CM may perform ahierarchical and/or peer-to-peer decision making. More specifically, inthe centralized topology, the super CM (i.e., master CM) may allocatesindependent channels to different CMs and the coexistence whitespace map(CWM) ma be used to indicate the channels to be used. in the Distributedtopology, the CMs are prioritized and classified with a certain policy,the CMs may report or send its preference on its operating channels tothe CDB or other CMs, and the coexistence whitespace map (CWM) may beused as an available channel set which the CM chooses operating channelsform.

In order to generate a decision making algorithm, the system (i.e.,802.19.1 system) should analyze obtained information, should be capableof making coexistence decisions, and should support differenttopologies. The information utilized in the decision making algorithmmay include, regardless the topology, bandwidth of each TV whitespace(TVWS) network/device or available channel lists seen from each TVWSnetwork/device and its corresponding power constraint on each TVWSchannel. The information may further include other information such asregulatory classes, system parameters, neighborhood information analyzedin advance, etc.

In addition to the above described function of a coexistence discoveryand information server (CDIS), the CDIS may convert the TVWS channelnumber (available channel set or coexistence map) to system's ownchannel number. (e.g., 802.11, 802. 16, 802. 22, etc) Further, inaddition to the above described function of coexistence manager (CM) ora master CM, the CM (or a master CM) may also convert the TVWS channelnumber (available channel set or coexistence map) to system's ownchannel number. (e.g., 802.11, 802. 16, 802. 22, etc).

The present disclosure provides an additional functional roles ofcoexistence discovery and information server (CDIS) and provides areference model for IEEE 802.19. Further, the present disclosureprovides service access points (SAPs) and primitives coexistence (COEX)function used for interfacing with other entities.

The coexistence discovery and information server (CDIS) may compute acoexistence contour in order to discover neighbor networks/systems.Also, the CDIS may make a coexistence whitespace map (CWM) for efficientfrequency resource sharing between different networks/systems. Further,the CDIS may control multiple operators in management related to a TVWScoexistence. Lastly, the CDIS may select a master coexistence manager(CM) in order to solve coexistence problems and to reduce communicationoverhead between the CMs.

An interface between the coexistence enabler (CE) and TVBD network ordevice may be referred to an interface A. Here, information notified foravailable resource may be communicated from the CE to the TVBD networkor device through the interface A. An interface between the coexistencemanager (CM) and the coexistence discovery and information server (CDIS)may be referred to an interface B2. Here, information required for acoexistence map (and/or information required for a neighbor set, and/orinformation notified for register/unregister, etc) may be communicatedfrom the CM to the CDIS through the interface B2. Also, informationnotified for coexistence map (and/or information notified for neighborset, and/or information notified for master CM, etc) may be communicatedfrom the CDIS to the CM through the interface B2. An interface betweencoexistence managers (CMs) may be referred to an interface B3. Here,information notified for register/unregister (from CM to a master CM,from CM (device) to CM (server)) may be communicated from the CM toother CM through the interface B3. Also, information notified forcoexistence map (from a master CM to CM, from CM (server) to CM(device)) and information required for policy exchange/negotiation maybe communicated between the CMs through the interface B3. An interfacebetween CM/CDIS and TVWS database may be referred to an interface C.Here, information notified for coexistence map (or information requiredfor available channel) may be communicated from the CDIS to TVWS DBthrough the interface C. Also, information notified forregister/unregister (or information required for available channel) maybe communicated from the CM to the TVWS DB through the interface C.Lastly, information notified for available channel may be communicatedfrom the TVWS DB to the CM/CDIS through the interface C.

FIG. 2 is an exemplary IEEE 802.19.1 reference model which the presentinvention is applied.

As illustrated in FIG. 2, the IEEE 802.19.1 reference model may include19.1 entity in a protocol stack interacting with other elements ofsystem. All exchanges between the 19.1 entity and other functionalentities may occur through service primitives grouped in service accesspoints (SAPs). The 19.1 entity may be defined as a set offunctionalities which is responsible for the coexistence of thedissimilar systems or independently operated networks/devices. Here, theservice access points (SAPs) may be defined as a set of primitives, andthe primitives may define the services. Within the definition of eachprimitive, there is a table of allowable parameters, and each parameteris defined using abstract data type.

A COEX_NET_SAP that support COEX information and message with the remote19.1 entity may be defined as the table 1. Theses parameters may supportthe interface B1, B2, B3, C, D.

TABLE 1 Service Primitive Category Description COEX_RegisterEntity EventTo register 19.1 Entity COEX_UnRegisterEntity Event To unregister 19.1Entity COEX_CMap Information To get Coexistence map COEX_CMap_CM_PUSHCommand To push Coexistence map COEX_CMap_CDIS_PUSH Command To pushCoexistence map COEX_AvailableChannels Information To get availablewhite space TV channel list COEX_AvailableChannel_TVDB_Push CommandCOEX_NeighborSet Information To get neighbor listCOEX_ResourceNegotiation Information Negotiate resourceCOEX_MasterCMSelection Command Select master CM

A COEX_LINK_SAP that media dependent interface of COEX function with thelower layers of the media specific protocol stacks may be defined as thetable 2. This parameter may support the interface A.

TABLE 2 Service Primitive Category DescriptionLINK_System_AvailableChannels Command Notify available channels set

A description of data formats and parameters will be given as following.

As shown in the table 1, the COEX_NET_SAP may include aCOEX_RegisterEntity primitive which is used by a 19.1 entity toregister. A COEX_RegisterEntity.request may be used for the CM toregister to another CM (i.e., a master CM, Server)/CDIS/TVWS DB, andthis may have parameters of SourIdentifier, DestinationIdentifier,SourceAddress, DestinationAddress, TxPower.ACOEX_RegisterEntity.response may have parameters of SourIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. TheCOEX_NET_SAP may include a COEX_UnRegisterEntity primitive which is usedby a 19.1 entity to unregister. A COEX_UnRegisterEntity.request may beused for the CM to unregister to another CM (i.e., a master CM,Server)/CDIS/TVWS DB, and this may have parameters of SourIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. ACOEX_UnRegisterEntity.response may have parameters of SourIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. TheCOEX_NET_SAP may include a COEX_CMap primitive which is used by a 19.1entity to get Coexistence Map. A COEX_CMap.request may be used for theCM/CE to request coexistence map to CM (i.e., a master CM, Server)/CDIS,this may be generated at any time during the lifetime of registration,and this may have parameters of SourIdentifier, DestinationIdentifier,SourceAddress, DestinationAddress, ChannelSet, Power. ACOEX_CMap.response may have parameters of SourIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. TheCOEX_NET_SAP may include a COEX_CMap_CM_PUSH primitive which is used bya 19.1 entity to get coexistence map. A COEX_CMap_CM_PUSH.request may beused for the CM(Master CM, Server) to push coexistence map to CM/CE,this may be generated at any time during the life time of registration,and this may have parameters of SoureIdentifier, DestinationIdentifier,SourceAddress, DestinationAddress, UpdateID, ChannelSet, Power. ACOEX_CMap_CM_PUSH.response may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress, UpdateID. TheCOEX_NET_SAP may include a COEX_CMap_CDIS_PUSH primitive which is usedby a 19.1 entity to get coexistence map. A COEX_CMap_CDIS_PUSH.requestmay be used for the CDIS to push coexistence map to CM/TVWS DB, this maybe generated at any time during the life time of registration, and thismay have parameters of SoureIdentifier, DestinationIdentifier,SourceAddress, DestinationAddress, UpdateID, ChannelSet, Power. ACOEX_CMap_CM_PUSH.response may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress, UpdateID. TheCOEX_NET_SAP may include a COEX_AvailableChannels primitive which isused by a 19.1 entity to get available TV channel list. ACOEX_AvailableChannels.request may be used for CM/CDIS to requestavailable channel list to TVWS DB, this may be generated at any timeduring the life time of registration, and this may have parameters ofSoureIdentifier, DestinationIdentifier, SourceAddress,DestinationAddress, UpdateID, ChannelSet, Power. ACOEX_AvailableChannels.response may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. TheCOEX_NET_SAP may include a COEX_AvailableChannel_TVDB_Push primitivewhich is used by a 19.1 entity to get available TV channel list. ACOEX_AvailableChannel_TVDB_Push.request may be used for the TVWS DB topush available channel list to CM/CDIS, this may be generated at anytime during the life time of registration, and this may have parametersof SoureIdentifier, DestinationIdentifier, SourceAddress,DestinationAddress, UpdateID, ChannelSet, Power. ACOEX_AvailableChannel_TVDB_Push.response may have parameters ofSoureIdentifier, DestinationIdentifier, SourceAddress,DestinationAddress, UpdateID. The COEX_NET_SAP may include aCOEX_NeighborSet primitive which is used by a 19.1 entity to getneighbor set. A COEX_NeighborSet.request may be used for CM to requestneighbor set to CDIS, this may be generated at any time during the lifetime of registration, and this may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress, NeighborSet. ACOEX_NeighborSet.response may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress. TheCOEX_NET_SAP may include a COEX_ResourceNegotiation primitive which isused by a 19.1 entity to negotiate resource. ACOEX_ResourceNegotiation.request may be used to negotiate resourcebetween CMs, this may be generated at any time during the life time ofregistration, and this may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress,CoexistencePolicy, ResourceInformation, ResourceNegotiationResult. ACOEX_ResourceNegotiation.response may have parameters ofSoureIdentifier, DestinationIdentifier, SourceAddress,DestinationAddress. The COEX_NET_SAP may include aCOEX_MasterCMSelection primitive which is used by a 19.1 entity toselect master CM. A COEX_MasterCMSelection.request may be used for CDISselects master CM and notifies information to CM, and this may haveparameters of SoureIdentifier, DestinationIdentifier, SourceAddress,DestinationAddress, MasterCMIdentifier. ACOEX_MasterCMSelection.response may have parameters of SoureIdentifier,DestinationIdentifier, SourceAddress, DestinationAddress.

As shown in the table 2, the COEX_LINK_SAP may include aLINK_System_AvailableChannels primitive which is used by a 19.1 entity(CM or CE) to push available resource information to Link Layer, andthis may be generated at any time during the life time of registration.A COEX_DB_Availablechannels.request may have parameters ofSystemIdentifier, ChannelSet, Power. ACOEX_DB_Availablechannels.response may have parameter ofSystemIdentifier.

This disclosure may provide a radio technology independent methods forcoexistence among dissimilar or independently operated TV Band Device(TVBD) networks and dissimilar TV Band Devices so as to enable thefamily of IEEE 802 Wireless Standards to effectively use TV White Spaceby providing standard coexistence methods among dissimilar orindependently operated TVBD networks and dissimilar TVBDs. Here, thestandard coexistence methods described in this disclosure will also beuseful for non IEEE 802 networks and TVBDs. As described above, the802.19.1 system architecture may have three logical entities (i.e.,Coexistence Manager (CM), Coexistence Enabler (CE), CoexistenceDiscovery and Information Server (CDIS)) and six logical interfaces(i.e., Interface A, Interface B1, Interface B2, Interface B3, InterfaceC, Interface D). Additionally, the 802.19.1 system may interact withthree external elements, such as TVWS database, TVBD network or device,and Operator Management Entity (OME).

In addition to the above described functionalities of the logicalentities, the coexistence enabler (CE) may has functional roles that 1)requesting and obtaining information (required for coexistence) fromTVBD network or device, 2) translating reconfiguration requests/commandand control information received from the CM into the TVBD specificreconfiguration requests/commands and send them to the TVBD network ordevice. The coexistence manager (CM) may has functional roles that 1)discovering of other CMs in order to solve coexistence problems betweenTVBD networks they serve, 2) making coexistence decision, which includesgenerating and providing corresponding coexistence requests/commands andcontrol information to the CE(s), 3) supporting exchange of informationrequired for coexistence among the CMs, which includes hierarchicaland/or peer-to-peer decision making capabilities in CM deployments, 4)selecting a master CM by sharing the information among the CMs, 5)making coexistence whitespace map (CWM) distributed topology forefficient frequency resource sharing between different networks/systems,6) assisting network operators in management related to TVWScoexistence. The coexistence discovery and information server (CDIS) mayhas functional roles that 1) making coexistence whitespace map (CWM)centralized topology for efficient frequency resource sharing betweendifferent networks/systems, 2) controlling multiple operators inmanagement related to TVWS coexistence, 3) selecting a master CM inorder to solve coexistence problems and reduce communication overheadbetween the CMs, 4) computing a coexistence contour in order to discoverneighbor networks/systems, 5) performing resource redirection in orderto solve coexistence problem, that is, the CDIS redirects the resource(C-MAP) to TVDB, 6) supporting the discovery of CMs to facilitateopening interfaces between the CMs, 7) collecting, aggregating, andproviding information facilitating coexistence, which includes datastorage and data processing.

In addition to the above description of the interfaces, the six logicalinterfaces in 802.19.1 system architecture may be split into threegroups. That is, the interface between 802.19.1 entities (i.e.,Interface B1, Interface B2, Interface B3) may be classified as a firstgroup, the interface between an 802.19.1 entity and TVBD network/device(i.e., Interface A) may be classified as a second group, and theinterface between 802.19.1 entities and TVWD database or OME (i.e.,Interface C, Interface D) may be classified as a third group. Here,different interfaces in each group may be distinguished by their usage,types of information exchanged, and underlying protocols.

Specifically, the interface A may be defined as an interface between CEand TVBD network or device. And, the followings may be communicated fromTVBD network or device via the interface A; 1) information required forcoexistence, 2) configuration/information requests for coexistence, 3)configuration/measurement/information responses for coexistence, 4)other information as needed. Also, the followings may be communicatedfrom the CE to TVBD network or device via the interface A; 1)reconfiguration requests/commands and control information (correspondingto coexistence requests/commands and control information received fromCM), 2) requests/commands related to control of measurements performedby TVBD network or device, 3) information notified for availableresource, 4) other information as needed. The interface B1 may bedefined as an interface between CE and CM. In addition, the followingsmay be communicated from the CE to the CM via the interface B1; 1)information required for coexistence (information obtained from TVBDnetwork or device), 2) other information as needed. Also, the followingsmay be communicated from the CE to the CE via the interface B1; 1)coexistence requests/commands and control information, 2) otherinformation as needed. The interface B2 may be defined as an interfacebetween CM and CDIS. And, the followings may be communicated from theFrom CM to CDIS via the interface B2; 1) information required forcoexistence map, 2) information required for coexistence map, 3)information required for neighbour set, 4) information notified forregister/unregister, 5) information required for discovery (obtained bythis CM), 6) information required for coexistence (obtained by this CM),7) other information as needed. Also, the followings may be communicatedfrom the CDIS to CM via the interface B2; 1) information notified forcoexistence map, 2) information notified for neighbour set, 3)information notified for master CM, 4) information required fordiscovery (obtained by other CMs), 5) information required forcoexistence (obtained by other CMs), 6) other information as needed. Theinterface B3 may be defined as an interface between CM and CM. And, thefollowings may be communicated from the from CM to CM via the interfaceB3; 1) information and message required for discovery and coexistence,2) information notified for register/unregister (from CM to Master CM,from CM(device) to CM(server)), 3) information notified for coexistencemap (from Master CM to CM, from CM(server) to CM(device)), 4)information required for policy exchange/negotiation, 5) otherinformation as needed. The interface C may be defined as an interfacebetween TVBD device and TVWS database. Moreover, the followings may becommunicated from the TVWS DB to TVBD device via the interface C; 1)information notified for available channel. The interface D may bedefined as an interface between CM and OME. Moreover, the followings maybe communicated from the OME to CM via the interface D; 1) networkoperator related information (e.g., spectrum policy/limitationsconcerning operator networks), 2) other information as needed.

A description of coexistence protocol frame format will be given asfollowing. In general, the coexistence protocol frame may be consistedof a coexistence frame header and a frame body. Here, a length of thecoexistence frame header field may have 8 octets, and a length of theframe body may have variable size.

The coexistence message frame formats may be differentiated by aninformation type field, which is in the octet immediately aftercoexistence frame header. The defined information frames are listed inTable 3.

TABLE 3 Information type field values Information type Description 0Reserved 1 Measurement request 2 Measurement report 3 Deenablementrequest 4 Transmit Power Adjustment request 5 Resource request 6Resource response 7 Resource announcement 8 Master CM frame 9 Registerframe format 10 Available channel set request 11 Available channel setresponse

The resource request is transmitted to the CM/master CM/CDIS to obtainresource allocation information for a local TVBD after it is initiatedand registered to the CM or to request updates on the previous resourceallocation, and the resource request frame format may be consisted of acoexistence frame header field, information type field, and reasonresult code field. Here, a length of the coexistence frame header fieldmay has 8 octets, and each of the information type field and reasonresult code field may has 1 octet respectively. Here, the value ofinformation type field may be set to five, and the reason result codefield is used to indicate the reason that a resource request frame wasgenerated. The length of the reason result code field is 1 octet. Thereason result codes may be defined as in Table 4.

TABLE 4 Reason Result Code field values Reason Result Code field valueDescription 0 Reserved 1 Reserved 2 Coexistence 3-255 Reserved

The resource response is sent in response to the resource request, andthe resource response frame format may be consisted of a coexistenceframe header field, information formation type field, and resourceresponse element field. Here, a length of the coexistence frame headerfield may have 8 octets, and a length of the information type field mayhave 1 octet, and a length of the resource response element field mayhave variable size. Here, the value of information type field may be setto 6, and the resource response elements field contains one or moreresource response elements. The number and length of the resourceresponse elements in a single resource response frame is limited by themaximum allowed CX protocol data unit (PDU) size, and length of theresource response element field is variable value subject to the lengthof resource information field. Here, a resource information type fieldmay be included in the resource response element field, and the resourceinformation type in the resource response element may indicatecoexistence MAP (CMAP) information. The CMAP response element frameformat may be consisted of a CMAP version field, length field, channelnumber field, and maximum power level field. Here, the channel numberfield may be set to the TV channel number which is available to use, andthe maximum power level may be a signed number and it has 1 octet inlength. This maximum power level may indicate the maximum transmit power(in dBm) allowed to be transmitted. Here, the channel number and maximumpower level fields may be repeated.

The resource announcement message is sent by a CM/master CM/CDIS toadvertise when it is changing resource allocation for one or more TVBDs,and the resource announcement frame format may be consisted of acoexistence header field, information type field, and a resourceannouncement elements field. The value of information type filed may beset to 7, and the resource announcement elements field may contain oneor more resource response elements. The number and length of theresource announcement elements in a single resource announcement framemay be limited by the maximum allowed CX protocol data unit (PDU) size.The length of the resource announcement elements field may has variablevalue subject to the length of the resource information field. Here, aresource information type field may be included in the resourceannouncement element field, and the resource information type in theresource announcement element may indicate CMAP information. The CMAPannouncement element frame format may be consisted of a MAP versionfield, length field, channel number field, and maximum power levelfield. Here, the channel number field may be set to the TV channelnumber which is available to use, and the maximum power level may be asigned number and it has 1 octet in length. This maximum power level mayindicate the maximum transmit power (in dBm) allowed to be transmitted.Here, the channel number and maximum power level fields may be repeated.

The master CM message is sent to CMs. The CDIS may advertise when it isselecting or changing a master CM, and the master CM frame format may beconsisted of a coexistence header field, information type field, and amaster CM announcement elements field. The value of information typefiled may be set to 8, and the master CM announcement elements field maycontain one or more master CM announcement elements. The number andlength of the master CM announcement in a single master CM announcementframe may be limited by the maximum allowed CX protocol data unit (PDU)size. The length of the master CM announcement elements field may hasvariable value subject to the length of resource information field.Here, a master CM information field may be included in the master CMannouncement element field, and the resource information type in themaster CM announcement element may indicate master CM information. Themaster CM announcement element frame format may be consisted of a masterCM version field, length field, and CM ID field.

The register message is sent by a CM/master CM/CDIS to register when itis registering TVBDs, and the register frame format may be consisted ofa coexistence header field, information type field, and a register TVBDelements field. The value of information type filed may be set to 9, andthe register TVBD element field may contain one or more resourceresponse elements. The number and length of the register element in asingle register TVBD frame may be limited by the maximum allowed CXprotocol data unit (PDU) size. The length of the register elements fieldmay has variable value subject to the length of resource informationfield. Here, a register information field may be included in theregister TVBD element field, and the resource information type in theregister TVBD element may indicate register information. The resourceinformation field corresponding to CMAP information may be consisted ofTVBD ID field, length field, transmit power level field, and locationinformation field.

The available channel set request message is transmitted to the CM toreport available channel set, and the available channel set requestframe format may be consisted of a coexistence header field, informationtype field, and a reason result code field. The value of informationtype filed may be set to 10, and the reason result code field is used toindicate the reason that a resource request frame was generated. Thelength of the reason result code field may have 1 octet, and the reasonresult codes may be defined as the Table 5.

TABLE 5 Reason Result Code field values Reason Result Code field valueDescription 0 Reserved 1 Reserved 2 Coexistence 3-255 Reserved

The available channel set response message is sent in response to theavailable channel set request message, and the available channel setresponse frame format may be consisted of a coexistence header field,information type field, and an available channel set element field. Thevalue of information type filed may be set to 11, and the availablechannel set elements field may contain one or more resource responseelements. The number and length of the available channel set elements ina single available channel set frame may be limited by the maximumallowed CX protocol data unit (PDU) size. The length of the availablechannel set elements field may has variable value subject to the lengthof resource information field. Here, the resource information type inthe resource response element may indicate CMAP information.

A procedures and protocols for information exchange according to thepresent disclosure will be described.

The exemplary procedures for a TVBD and CM discovery will be explainedhereafter.

FIG. 3 is an exemplary procedure for TVBD discovery which the presentinvention is applied. As illustrated in FIG. 3, the coexistence enabler(CE) may get capability from the TVBD. Thereafter, the CE may registerto the coexistence manager (CM). Namely, in the TVBD discoveryprocedure, the CE gets capability from the TVBD and reports capabilityof the TVBD to the CM.

FIG. 4 is an exemplary procedure for coexistence manager (CM) discoverwhich the present invention is applied. As illustrated in FIG. 4, the APmay register to the TVDB and the CM, and then the CM may register to thecoexistence discovery and information server (CDIS). Thereafter, theCDIS may request the available TV channel list from the TVWS DB. Here,such request may be performed by transmitting an available TVWS channellist request. Alternatively, the CDIS may periodically receive theavailable TV channel list from the TVDB. Thereafter, the CDIS maycalculates neighbor of CMs, and then may notify discover information tothe CMs. Namely, in the CM discovery procedure, after registration ofdevice and getting an available channel set, the CDIS calculatesneighbor set and notifies information of the neighbor set to the CM.

FIG. 5 is another exemplary procedure for coexistence manager (CM)discover which the present invention is applied;

As illustrated in FIG. 5, the AP may register to the TVDB (or TVWS DB)and the CM, and then the CM may register to the coexistence discoveryand information server (CDIS). Thereafter, the CDIS may directly receiveor obtain an available TVWS channel list from the TVWS DB. Or, the CMmay transmit a coexistence information request to the TVBD, and mayreceive a coexistence information response containing the available TVWSchannel list. Thereafter, the available TVWS channel list may bedelivered to the CDIS, and the CDIS may calculates neighbor of CMs, andthen may notify discover information to the CMs.

The exemplary procedures for centralized topology will be explainedhereafter.

FIG. 6 is a first exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 6, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the AP may request the resource to the CDIS, and then theCDIS may request the available TV channel list from the TVDB. Here, suchrequest may be performed by transmitting an available TVWS channel listrequest. Alternatively, the CDIS may periodically receive the availableTV channel list from the TVDB. Thereafter, the CDIS may calculateneighbor of CMs, and may allocate the resource (i.e., C-MAP) to the AP.Namely, the AP requests resources, and the CDIS gets available channellists from the TVDB, and then the CDIS assigns the resources to the AP.

FIG. 7 is a second exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 7, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. Thereafter, the CDIS may calculate neighbor ofCMs, and may allocate the resource (i.e., C-MAP). Thereafter, the CDISmay push or transmit the resource (C-MAP) to the AP. Namely, the CDISgets available channel lists from the TVDB at regular intervals andpushes the resources to AP.

FIG. 8 is a third exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 8, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. Or, the CDIS may transmit a coexistenceinformation request to the TVBD, and may receive a coexistenceinformation response containing the available TVWS channel list.Thereafter, the CDIS may calculate neighbor of CMs, and may allocate theresource (i.e., C-MAP). Thereafter, the CDIS may push or transmit theresource (C-MAP) to the AP. Namely, the CDIS gets available channellists from the TVDB at regular intervals and pushes the resources to AP.

FIG. 9 is a fourth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 9, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. Thereafter, the CDIS may calculate neighbor ofCMs, and may allocate the resource (i.e., C-MAP). Thereafter, the AP mayrequest the resource to the CDIS, and the CDIS may allocate the resource(C-MAP) to the AP. Namely, the CDIS gets available channel lists fromthe TVDB at regular intervals and assign the resource by request.

FIG. 10 is a fifth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 10, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. Or, the CDIS may transmit a coexistenceinformation request to the TVBD, and may receive a coexistenceinformation response containing the available TVWS channel list.Thereafter, the CDIS may calculate neighbor of CMs, and may allocate theresource (i.e., C-MAP). Thereafter, the AP may request the resource tothe CDIS, and the CDIS may allocate the resource (C-MAP) to the AP.

FIG. 11 is a sixth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) which the presentinvention is applied. As illustrated in FIG. 11, the AP may register tothe TVDB and the coexistence discovery and information server (CDIS).Thereafter, the AP may request the resource to the CDIS, and the CDISmay get information of available TV channel list from the TVDB. Here,the TVDB may update the available TV channel list at regular intervals.Thereafter, the CDIS may calculates neighbor of CMs, and may allocatethe resource (i.e., C-MAP) to the AP. Namely, the AP requests resourcesand the CDIS gets available channel lists from the TVDB at regularintervals and then assign the resource.

FIG. 12 is a first exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied. Asillustrated in FIG. 12, the AP may register to the TVDB and thecoexistence discovery and information server (CDIS), and the CM mayregister to the CDIS. Thereafter, the AP may request the resource to theCM, and the CM may request the information of neighbor list andresources (C-MAP) to the CDIS. Thereafter, the CDIS may requestavailable TV channel list from the TVDB. Then, the CDIS may calculateneighbor of CMs and the resource (i.e., C-MAP). Thereafter, the CDIS maynotify to the CM about the neighbor list of CMs and the resources(C-MAP), and the CM may allocate the resources (C-MAP) to the AP.Namely, the AP requests resources and the CDIS gets available channellists from the TVDB then inform to the CM. In this procedure, the CMassigns the resources.

FIG. 13 is a second exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied. Asillustrated in FIG. 13, the AP may register to the TVDB and thecoexistence discovery and information server (CDIS), and the CM mayregister to the CDIS. Thereafter, the AP may request the resource to theCM, and the CM may request the information of neighbor list andresources (C-MAP) to the CDIS. Thereafter, the CDIS may requestavailable TV channel list from the TVDB. Or, the CM may transmit acoexistence information request to the TVBD, and may receive acoexistence information response containing the available TVWS channellist. Thereafter, the available TVWS channel list may be delivered tothe CDIS, and the CDIS may calculate neighbor of CMs, and then maycalculate neighbor of CMs and the resource (i.e., C-MAP). Thereafter,the CDIS may notify to the CM about the neighbor list of CMs and theresources (C-MAP), and the CM may allocate the resources (C-MAP) to theAP. Namely, the AP requests resources and the CDIS gets availablechannel lists from the TVDB then inform to the CM.

FIG. 14 is a third exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied. Asillustrated in FIG. 14, the AP may register to the TVDB and thecoexistence discovery and information server (CDIS), and the CM mayregister to the CDIS. Thereafter, the CDIS may get the information ofavailable TV channel list from the TVDB. Here, the CM may receive theavailable TV channel list from the TVBD through a coexistenceinformation request, and the TVBD may deliver the available TV channellist to the CDIS via the CM through a coexistence information response.Here, the TVDB may update the available TV channel list at regularintervals. Then, the CDIS may calculate neighbor of CMs and the resource(i.e., C-MAP). Thereafter, the CDIS may push to the CM that informationof the neighbor list of CMs and the resources (C-MAP), and the CM mayallocate the resources (C-MAP) to the AP. Namely, the CDIS getsavailable channel lists from the TVDB at regular intervals and pushesresources to the CM, and the CM assigns the resource.

FIG. 15 is a fourth exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with singlecoexistence enabler (CE) which the present invention is applied. Asillustrated in FIG. 15, the AP may register to the TVDB and thecoexistence discovery and information server (CDIS), and the CM mayregister to the CDIS. Thereafter, the AP may request the resources tothe CM, and the CM may request the information of neighbor list and theresources (C-MAP) to the CDIS. Thereafter, the CDIS may get theinformation of available TV channel list from the TVDB. Here, the TVDBmay update the available TV channel list at regular intervals. Then, theCDIS may calculate neighbor of CMs and the resource (i.e., C-MAP).Thereafter, the CDIS may notify to the CM about the neighbor list of theCMs and C-MAP, and the CM may allocate the resources (C-MAP) to the AP.Namely, the AP requests the resource and the CDIS gets available channellists from the TVDB at regular intervals then informs to the CM. In thisprocedure, the CM assigns the resource.

FIG. 16 is an exemplary procedure for resource allocation by acoexistence discovery and information server (CDIS) with multiplecoexistence enablers (CEs) which the present invention is applied. Asillustrated in FIG. 16, the AP may register to the TVDB and thecoexistence discovery and information server (CDIS), and the CM mayregister to the CDIS. Thereafter, the AP may request the resources tothe CM, and the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. Then, the CDIS may calculate neighbor of CMs andthe resource (i.e., C-MAP). Thereafter, the CDIS may notify to the CMabout the neighbor list of the CMs and C-MAP, and the CM may allocatethe resources (C-MAP) to the AP. Namely, in this procedure, the CDISgets available channel lists from the TVDB at regular intervals andpushes resources to the CM, and the CM assign the resource.

FIG. 17 is a first exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied. As illustrated in FIG. 17, theAP may register to the TVDB and the coexistence manager (CM), and the CMmay register to the master CM. Thereafter, the master CM may register tothe CDIS. The AP may request the resources to the CM, and the CM mayrequest the information of neighbor list and the resources (C-MAP) tothe master CM. Thereafter, the master CM may request the information ofneighbor list and the resources to the CDIS, and the CDIS may requestthe available TV channel list from the TVDB. Then, the CDIS maycalculate the neighbor of the CMs and the resources (C-MAP), and mayinform to the master CM about neighbor list of the CMs and C-MAP. Afterthis, the master CM may allocate the resources (C-MAP) to the CM, andthe CM may notify to the AP about the resources (C-MAP). Namely, in thisprocedure, the AP requests resources and the CDIS gets available channellists from the TVDB then informs to the master CM, and the master CMassigns the resources to the CM.

FIG. 18 is a second exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied. As illustrated in FIG. 18, theAP may register to the TVDB and the coexistence manager (CM), and the CMmay register to the master CM. Thereafter, the master CM may register tothe CDIS. The CDIS may get information of available TV channel list fromthe TVDB. Here, the TVDB may update available TV channel list at regularintervals. Then, the CDIS may calculate the neighbor of the CMs and theresources (C-MAP), and the AP may request the resources to the CM.Thereafter, the CM may request the information of neighbor list and theresources to the master CM, and the master CM may request theinformation of the neighbor list and the resources to the CDIS. Then,the CDIS may inform to the master CM about the neighbor list of the CMsand C-MAP, the master CM may allocate the resources (C-MAP) to the CM,and the CM may notify to the AP about the resources (C-MAP). Namely, inthis procedure, the CDIS gets available channel lists from the TVDB atregular intervals and informs the resources by request, and the masterCM assigns the resources to the CM.

FIG. 19 is a third exemplary procedure for resource allocation by amaster coexistence manager (CM) with single coexistence enabler (CE)which the present invention is applied. As illustrated in FIG. 19, theAP may register to the TVDB and the coexistence manager (CM), and the CMmay register to the master CM. Thereafter, the master CM may register tothe CDIS. The CDIS may get information of available TV channel list fromthe TVDB. Here, the TVDB may update available TV channel list at regularintervals. Then, the CDIS may calculate the neighbor of the CMs and theresources (C-MAP), and the CDIS may inform to the master CM aboutneighbor list of the CMs and the resources (C-MAP). Thereafter, themaster CM may allocate the resource (C-MAP) to the CM, and then themaster CM may push to the information of neighbor list of the CMs andthe C-MAP to the CM. Thereafter, the CM may push to the information ofneighbor list of the CMs and the resources (C-MAP) to the AP. Namely, inthis procedure, the CDIS gets available channel lists from the TVDB atregular intervals and then informs to the master CM, and the master CMpushes the resources to the CM.

FIG. 20 is an exemplary procedure for resource allocation by a mastercoexistence manager (CM) with multiple coexistence enablers (CEs) whichthe present invention is applied. As illustrated in FIG. 20, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the master CM. Thereafter, the master CM may register to theCDIS. The CDIS may get information of available TV channel list from theTVDB. Here, the TVDB may update available TV channel list at regularintervals. Then, the CDIS may calculate the neighbor of the CMs and theresources (C-MAP), and the CDIS may inform to the master CM aboutneighbor list of the CMs and the resources (C-MAP). Thereafter, themaster CM may allocate the resource (C-MAP) to the CM, and then themaster CM may push to the information of neighbor list of the CMs andthe C-MAP to the CM. Thereafter, the CM may reallocate the resource(C-MAP) to the CMs under the CM's network. Namely, in this procedure,the CDIS gets available channel lists from the TVDB at regular intervalsand then informs to the master CM, and the master CM assigns theresources to the CM, and the CM reassigns the resources.

FIG. 21 is an exemplary procedure for resource allocation by a TVWSdatabase (DB) which the present invention is applied. As illustrated inFIG. 21, the AP may register to the TVDB and the coexistence discoveryand information server (CDIS). Thereafter, the CDIS may get informationof available TV channel list from the TVDB. Here, the TVDB may updateavailable TV channel list at regular intervals. Then, the CDIS maycalculate the neighbor of the CMs and the resources (C-MAP), and theCDIS may notify the C-MAP to the TVWS DB. Thereafter, the TVDB mayannounce the information.

The exemplary procedures for distributed topology will be explainedhereafter.

FIG. 22 is a first exemplary procedure for distributed topology, whichthe present invention is applied. As illustrated in FIG. 22, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS).Thereafter, the AP may request the resources (C-MAP) to the CM, and theCM may request the information of neighbor list and the resources(C-MAP) to the CDIS. The CDIS may request the available TV channel listfrom the TVDB, and may calculate the neighbor of CMs and the resources(C-MAP). The CDIS may inform to the CM about neighbor list of CMs andC-MAP. Thereafter, the CM may negotiate resources among the CMs and mayreallocate the resource (C-MAP) to the AP. Here, the AP requests theresources and the CDIS gets available channel lists from the TVDB theninform to the CM. The CM negotiates the resource with the CMs.

FIG. 23 is a second exemplary procedure for distributed topology, whichthe present invention is applied. As illustrated in FIG. 23, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS).Thereafter, the CDIS may get information of available TV channel listfrom the TVDB. Here, the TVDB may update the available TV channel listat regular intervals. The CDIS may calculate the neighbor of the CMs andthe resources (C-MAP), and may inform to the CM about the neighbor listof the CMs and resources (C-MAP). Thereafter, the AP may request theresources to the CM. The CM may negotiate the resources among the CMs,and may reallocate the resources (C-MAP) to the AP. Here, the CDIS getsavailable channel lists from the TVDB at regular intervals and informsthe resources to the CM. The CM negotiates the resources with the CMs.

FIG. 24 is a third exemplary procedure for distributed topology, whichthe present invention is applied. As illustrated in FIG. 24, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS). TheAP may request the resources (C-MAP) to the CM, and the CM may requestthe information of the neighbor list and resources to the CDIS.Thereafter, the CDIS may request the available TV channel list from theTVDB, and may calculate the neighbor of the CMs and C-MAP. The CDIS mayinform to the CM about the neighbor list of the CMs and C-MAP.Thereafter, the CM may negotiate the resources among the CMs. The CM mayrecalculate neighbor and reallocate the resource (C-MAP) to the AP.Here, the AP requests the resources and the CDIS gets available channellists from the TVDB then inform to the CM. The CM negotiates theresources with the CM, and the CM discovers the neighbor and reassignsthe resource.

FIG. 25 is a fourth exemplary procedure for distributed topology, whichthe present invention is applied. As illustrated in FIG. 25, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS). TheAP may request the resources (C-MAP) to the CM, and the CDIS may getinformation of available TV channel list from the TVDB. Here, the TVDBmay update available TV channel list at regular intervals. The CDIS maycalculate the neighbor of CMs and C-MAP, and the CDIS may inform to theCM about the neighbor list of the CMs and the C-MAP. Thereafter, the APmay request the resource to the CM, and the CM may negotiate theresources among the CMs. The CM may recalculate the neighbor and mayreallocate the resources (C-MAP) to the AP. Here, the CDIS getsavailable channel lists from the TVDB at regular intervals and informsthe resources to the CM, the CM negotiates the resources with the CMs.The CM discovers the neighbor and reassigns the resources.

The exemplary procedures for Hybrid topology will be explainedhereafter.

FIG. 26 is an exemplary procedure for Hybrid topology, which the presentinvention is applied. As illustrated in FIG. 26, the AP may register tothe TVDB and the coexistence manager (CM), and the CM may register tothe coexistence discovery and information server (CDIS). The CDIS/CMsmay get information of available TV channel list form the TVDB. Here,the TVDB may update available TV channel list at regular intervals.Thereafter, the CDIS may calculate the neighbor of CMs and resources(C-MAP). The CMs may report the channel list set, and the CDIS may checkpriority table in conflict of case. Then, the CDIS may send confirmationinformation to CM1 and may request for changing a new channel list set.The CM2 may change channel list set and may report the new channel listset. Thereafter, the CDIS may send the confirmation.

The exemplary procedures for a master CM selection will be explainedhereafter.

FIG. 27 is a first exemplary procedure for a master CM selection, whichthe present invention is applied. As illustrated in FIG. 27, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS). TheCDIS may get information of available TV channel list form the TVDB.Here, the TVDB may update available TV channel list at regularintervals. Thereafter, the CDIS may calculate the neighbor of CMs andresources (C-MAP). Then, the CDIS may select the master CM, and mayannounce to the CMs. Here, the CDIS gets available channel lists fromthe TVDB and calculates neighbor of the CMs and resources (C-MAP) thenannounces the master CM to the CMs.

FIG. 28 is a second exemplary procedure for a master CM selection, whichthe present invention is applied. As illustrated in FIG. 28, the AP mayregister to the TVDB and the coexistence manager (CM), and the CM mayregister to the coexistence discovery and information server (CDIS). TheCDIS may get information of available TV channel list form the TVDB.Here, the TVDB may update available TV channel list at regularintervals. Thereafter, the CDIS may calculate the neighbor of CMs andresources (C-MAP). Then, the CDIS may inform to the CMs about theneighbor list of the CMs. Thereafter, The CM may negotiate the resourcesamong the CMs, and may select the master CM. Here, the CDIS calculatesthe neighbor of the CMs and resources (C-MAP) then informs to the CMs.The CM negotiates the master CM policy with the CMs.

The exemplary procedures for a coexistence MAP (resource allocation)will be explained hereafter.

FIG. 29 is an exemplary procedure for resource allocated by registerinformation in centralized topology, which the present invention isapplied. As illustrated in FIG. 29, the TVBD device may register to theCM and the CDIS/master CM. Thereafter, the CDIS/master CM may allocatethe resources (C-MAP) to the CM and TVBD device. Namely, this procedureprocesses a resource allocation by the CDIS/master CM. In addition, theTVBD device requests the resources and the CDIS/master CM gets registerinformation from the TVDB device then assigns the resources.

FIG. 30 is an exemplary procedure for resource allocated by availablechannel set in centralized topology, which the present invention isapplied. As illustrated in FIG. 30, the TVBD device may request theresource(s), and the CM may request the available TV channel set to theTVBD device. Thereafter, the TVBD device may response or update theavailable channel set, and the CDIS/master CM may allocate the resource(C-MAP) to the CM and TVBD device. Namely, this procedure processes aresource allocation by the CDIS/master CM. In addition, the TVBD devicerequests the resources and the CDIS/master CM gets register informationand available channel set from the TVDB device then assigns theresource.

FIG. 31 is an exemplary procedure for resource allocated by registerinformation in distributed topology, which the present invention isapplied. As illustrated in FIG. 31, the TVBD device may register to theCM, and the CM may allocate the resources (C-MAP) to the TVBD device.Namely, this procedure processes a resource allocation by registerinformation in distributed topology.

FIG. 32 is an exemplary procedure for resource allocated by availablechannel set in distributed topology, which the present invention isapplied. As illustrated in FIG. 32, the TVBD device may request theresource (C-MAP), and the CM may request the available TV channel set tothe TVBD device. Thereafter, the TVBD device may response or update theavailable channel set, and the CM may allocate the resource (C-MAP) tothe TVBD device. Namely, this procedure processes a resource allocationby available channel set in distributed topology.

According to the present disclosure, the decision on resource allocationamong dissimilar or independently operated TVBD networks and dissimilarTVBDs may be made by a CM/Master or a CM/CDIS. The CM/Master CM/CDIS maymake a resource announcement to its registered CEs, and the announcedCEs may take an appropriate action on the operating channel of TVBD sothat the TVBD do not use any resources. The resource information may beindicated in the form of channel numbers and corresponding power limitsor time scheduling information in case CEs can operate in time-sharing.

According to the present disclosure, upon receipt of aCOEX_Resource_Announcement.request primitive, the coexistence manager(CM) may create and transmit a resource announcement frame to the CEs.The resource announcement frame may be sent to the CE when an optimizedresource allocation for the CE has been updated based on the measurementreports obtained from the CEs or TVWS DB data obtained from the CEs orthrough a direct access to the TVWS DB. The CM may make use of theinformation in received TVBD detection report and incumbent userdetection reports sent by remote CEs or obtained by performingmeasurement itself and the additional information obtained though directaccess to the TVWS DB or CDIS. For example, theCOEX_Resource_Announcement.request may be initiated when a TVBDinterferes with the other TVBD severely and either one of them or bothof them sends TVBD detection report complaining about it. Anotherexample may be in case that when the TVBD operates on illegal channelsand the CM detects the illegal operation after receiving TVBD detectionreport on unpermitted channels.

The channel number field in a C-MAP announcement element may indicatethe available channel that the receiving TVBD can use. The maximum powerlevel field in the C-MAP announcement element may indicate the maximumallowed transmitting power level on the channel. In addition, thechannel number and maximum power level field may be repeated to addressmore than one TV channel that is available for the receiver. The channelnumbers in resource announcement frame may be a subset of availablechannel list of the TVBD, wherein the receiving CE resides. The CM mayobtain available channel list of the TVBDs so as to allocate resourcesto the CEs by means of accessing TVWS DB directly or requestingavailable channel list to the CEs.

Upon receipt of a resource announcement frame with C-MAP announcementelement, the receiving CE may issue theCOEX_Resource_Announcement.indication primitive to inform the TVBDmanagement entity of the resource updates from the CM. Also, uponreceipt of COEX_Resource_Announcement.indication primitive, the TVBDmanagement entity may invoke a media specific primitive which is usedfor indicating updates of the available channel list obtained from TVWSDB. The media specific management entity may take appropriate action onreceipt of channel list update such as a dynamic frequency selection.

The present disclosure may provide a method of allocating a resource inwireless communication system, the method comprising: receiving, by acoexistence discovery and information server (CDIS) entity, at least oneavailable resource from a TV database (TVDB) entity; performing, by theCDIS entity, a neighbor set calculation based on the received at leastone available resource, wherein the neighbor of at least one coexistencemanager (CM) entity is calculated by the neighbor set calculation; andcalculating, by the CDIS entity, the resource according to the neighborset calculation, wherein the calculated resource is allocated to atleast one TV band device (TVBD), wherein the at least one receivedavailable resource is an available TV whitespace channel list or awhitespace map, the at least one received available resource is receivedafter transmitting a request for the available resource to the TVDBentity, the at least one received available resource is periodicallyreceived from the TVDB entity, the neighbor set calculation includes acomputation of a coexistence contour to discover the neighbor of the atleast one CM entity, the resource is calculated by making a coexistencewhitespace map (CWM), the calculated resource is allocated to the atleast one TVBD entity by the CDIS entity, the neighbor set calculationand the calculated resource are notified to at least one coexistencemanager (CM) entity, and the at least one CM entity allocates theresource to the at least one TVBD entity, the at least one CM entity isa master CM entity selected from a plurality of CM entities, the masterCM entity is selected by the CDIS entity, and the neighbor setcalculation and the calculated resource are notified to the TVDB entity,and the TVDB entity announces the allocated resource to at least oneTVBD.

Also, it can be said that the present disclosure may provide anapparatus for allocating a resource in wireless communication system,the apparatus comprising: a controller to perform the steps of;receiving at least one available resource from a TV database (TVDB)entity; performing a neighbor set calculation based on the received atleast one available resource, wherein the neighbor of at least onecoexistence manager (CM) entity is calculated by the neighbor setcalculation; and calculating the resource according to the neighbor setcalculation, wherein the calculated resource is allocated to at leastone TV band device (TVBD).

Hereinafter, a terminal or a device in accordance with the presentinvention will be described.

Although the present disclosure is described in the context of mobilecommunications, the present disclosure may also be used in any wirelesscommunication systems using mobile devices, such as PDAs and laptopcomputers equipped with wireless communication capabilities (i.e.interface). Moreover, the use of certain terms to describe the presentdisclosure is not intended to limit the scope of the present disclosureto a certain type of wireless communication system. The presentdisclosure is also applicable to other wireless communication systemsusing different air interfaces and/or physical layers, for example,TDMA, CDMA, FDMA, WCDMA, OFDM, EV-DO, Wi-Max, Wi-Bro, etc.

The exemplary embodiments may be implemented as a method, apparatus orarticle of manufacture using standard programming and/or engineeringtechniques to produce software, firmware, hardware, or any combinationthereof. The term “article of manufacture” as used herein refers to codeor logic implemented in hardware logic (e.g., an integrated circuitchip, Field Programmable Gate Array (FPGA), Application SpecificIntegrated Circuit (ASIC), etc.) or a computer readable medium (e.g.,magnetic storage medium (e.g., hard disk drives, floppy disks, tape,etc.), optical storage (CD-ROMs, optical disks, etc.), volatile andnon-volatile memory devices (e.g., EEPROMs, ROMs, PROMs, RAMs, DRAMs,SRAMs, firmware, programmable logic, etc.).

Code in the computer readable medium may be accessed and executed by aprocessor. The code in which exemplary embodiments are implemented mayfurther be accessible through a transmission media or from a file serverover a network. In such cases, the article of manufacture in which thecode is implemented may comprise a transmission media, such as a networktransmission line, wireless transmission media, signals propagatingthrough space, radio waves, infrared signals, etc. Of course, thoseskilled in the art will recognize that many modifications may be made tothis configuration without departing from the scope of the presentdisclosure, and that the article of manufacture may comprise anyinformation bearing medium known in the art.

As the present disclosure may be embodied in several forms withoutdeparting from the spirit or essential characteristics thereof, itshould also be understood that the above-described embodiments are notlimited by any of the details of the foregoing description, unlessotherwise specified, but rather should be construed broadly within itsspirit and scope as defined in the appended claims, and therefore allchanges and modifications that fall within the metes and bounds of theclaims, or equivalents of such metes and bounds are therefore intendedto be embraced by the appended claims.

1. A method of allocating a resource in wireless communication system,the method comprising: receiving, by a coexistence discovery andinformation server (CDIS) entity, at least one available resource from aTV database (TVDB) entity; performing, by the CDIS entity, a neighborset calculation based on the received at least one available resource,wherein the neighbor of at least one coexistence manager (CM) entity iscalculated by the neighbor set calculation; and calculating, by the CDISentity, the resource according to the neighbor set calculation, whereinthe calculated resource is allocated to at least one TV band device(TVBD).
 2. The method of claim 1, wherein the at least one receivedavailable resource is an available TV whitespace channel list or awhitespace map.
 3. The method of claim 1, wherein the at least onereceived available resource is received after transmitting a request forthe available resource to the TVDB entity.
 4. The method of claim 1,wherein the at least one received available resource is periodicallyreceived from the TVDB entity.
 5. The method of claim 1, wherein theneighbor set calculation includes a computation of a coexistence contourto discover the neighbor of the at least one CM entity.
 6. The method ofclaim 1, wherein the resource is calculated by making a coexistencewhitespace map (CWM).
 7. The method of claim 1, wherein the calculatedresource is allocated to the at least one TVBD entity by the CDISentity.
 8. The method of claim 1, wherein the neighbor set calculationand the calculated resource are notified to at least one coexistencemanager (CM) entity, and the at least one CM entity allocates theresource to the at least one TVBD entity.
 9. The method of claim 8,wherein the at least one CM entity is a master CM entity selected from aplurality of CM entities.
 10. The method of claim 9, wherein the masterCM entity is selected by the CDIS entity.
 11. The method of claim 1,wherein the neighbor set calculation and the calculated resource arenotified to the TVDB entity, and the TVDB entity announces the allocatedresource to at least one TVBD.
 12. The method of claim 1, wherein allsteps are implemented in IEEE 802.19.1.
 13. An apparatus for allocatinga resource in wireless communication system, the apparatus comprising: acontroller to perform the steps of; receiving at least one availableresource from a TV database (TVDB) entity; performing a neighbor setcalculation based on the received at least one available resource,wherein the neighbor of at least one coexistence manager (CM) entity iscalculated by the neighbor set calculation; and calculating the resourceaccording to the neighbor set calculation, wherein the calculatedresource is allocated to at least one TV band device (TVBD).